Add parser for FLAG (fka Global Cloud Xchange)#419
Merged
Conversation
i3dnet-akoopen
requested review from
glennmatthews,
jvanderaa,
pke11y and
scetron
as code owners
i3dnet-akoopen
changed the title
jvanderaa
reviewed
May 15, 2026
Contributor
|
Let's keep the old parser for now. And then we can create an issue here to clean it up in a period of time. I can do that as we get this merged. |
…enance-parser into flag-parser
Contributor
Author
|
Included suggestions. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Globalcloudexchange (Gcx) has rebranded to FLAG and with this their email format has changed slightly. I have started off with the Gcx parser and made the required changes to make it work.
Potentially the current Gcx parser could be deleted, but I'm unsure what the best way forward for this would be.
Good to note: FLAG can send multiple windows in the same email; however, it is not trivial to de-duplicate the maintenance data with only the HTML data. The maintenance_id and status only exist within the email subject parser, so the HTML parser doesn't know. For now, the HTML parser will only take the latest listed window. From what I have seen so far, FLAG only lists one window in their emails, but the format of course suggests otherwise...